Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Beaconsfield District Council (No.10) Tree Preservation Order 1974; dated 31/12/74; under Sections 6

reference
ZZZZZWESRW962
name
Beaconsfield District Council (No.10) Tree Preservation Order 1974; dated 31/12/74; under Sections 6
tree-preservation-order

undefined

TPO/BD/1974/10
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.662657 51.489593,-0.662759 51.489534,-0.662898 51.489431,-0.663008 51.489332,-0.663045 51.489290,-0.663056 51.489256,-0.663057 51.489225,-0.663040 51.489194,-0.662977 51.489164,-0.662902 51.489148,-0.662717 51.489146,-0.662455 51.489183,-0.662412 51.489196,-0.662383 51.489215,-0.662382 51.489249,-0.662401 51.489320,-0.662429 51.489354,-0.662448 51.489414,-0.662450 51.489468,-0.662432 51.489568,-0.662440 51.489593,-0.662474 51.489623,-0.662548 51.489639,-0.662606 51.489630,-0.662637 51.489614,-0.662657 51.489593)),((-0.663893 51.488593,-0.663924 51.488565,-0.663938 51.488533,-0.663926 51.488483,-0.663898 51.488454,-0.663831 51.488426,-0.663660 51.488390,-0.663485 51.488379,-0.663384 51.488393,-0.663306 51.488436,-0.663278 51.488476,-0.663273 51.488498,-0.663273 51.488520,-0.663291 51.488562,-0.663339 51.488640,-0.663387 51.488685,-0.663486 51.488733,-0.663589 51.488750,-0.663703 51.488742,-0.663762 51.488726,-0.663893 51.488593)))
point
POINT (-0.663098 51.488991)
notes
organisation
entry-date
2017-07-04
start-date
2017-07-04
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL